Repository navigation
web: surface OIDC session expiry instead of stalling; recover kickoff plan request - #4
Merged
Merged
Conversation
… plan request
When the edge access session expires mid-build, both transports followed the
IAM redirect (or saw a 401), then returned a never-settling promise after
assign('/'). BuildPage rendered only initial-load errors, so the cached
running turn kept showing 「考えています」 indefinitely; on Craftsman this
hid a completed kickoff for 41 minutes (draft-41cb28ef, 01:56Z→02:37Z).
- One session-expiry detector for Platform proxy and Console API: 401,
manual/opaque/followed redirects, HTML login bodies → settled
SESSION_EXPIRED error, no retries, latch blocks further requests.
- Root-level boundary unmounts polling and shows 「セッションが切れました。
再サインインしてください」 with 「再サインイン」 to the same draft URL.
- Kickoff recovery: a succeeded kickoff turn with no plan requests the
generation from server history (idempotent key), and an idle unplanned
draft offers 「この内容で提案して」 as the primary action instead of
showing nothing.
- Active draft polling continues in background tabs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When the edge access session expires mid-build, both transports followed the
IAM redirect (or saw a 401), then returned a never-settling promise after
assign('/'). BuildPage rendered only initial-load errors, so the cached
running turn kept showing 「考えています」 indefinitely; on Craftsman this
hid a completed kickoff for 41 minutes (draft-41cb28ef, 01:56Z→02:37Z).
manual/opaque/followed redirects, HTML login bodies → settled
SESSION_EXPIRED error, no retries, latch blocks further requests.
再サインインしてください」 with 「再サインイン」 to the same draft URL.
generation from server history (idempotent key), and an idle unplanned
draft offers 「この内容で提案して」 as the primary action instead of
showing nothing.